Creating real-time conversations

ABSTRACT

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for creating conversations related to a location. One method includes receiving a topic for a real-time conversation from a user, receiving location information related to a location of the user, and creating a real-time conversation object that includes the received topic. The method also includes tagging the created real-time conversation object with the received location information, indexing, based on the received topic and the received location information, the tagged real-time conversation object with respect to other real-time conversation objects, and providing the tagged real-time conversation object in response to a search for real-time conversation objects received from another user.

RELATED APPLICATION DATA

This application claims the benefit under 35 U.S.C. §119(e) of U.S.Provisional Patent Application No. 61/582,104, entitled “CreatingReal-Time Conversations,” filed Dec. 30, 2011; the disclosure of whichis incorporated herein by reference in its entirety.

BACKGROUND

This specification relates to the creation of a conversation in anonline environment. The Internet has provided a medium for many newforms of communication. From e-mail to chat rooms to instant messaging,Internet users have the ability to talk to one or many of their friendswithin moments from anywhere in the world. Moreover, as computingdevices have become smaller and wireless, these new forms ofcommunication have become increasingly mobile.

SUMMARY

Users can quickly share information about places, things, and eventsthat occur nearby the users, by creating real-time online conversations.For each conversation created by a user, a server can create aconversation object that is tied to a geographic location and a time,and can index the conversation object such that the conversation can beeasily found by other users that are near the location shortly after theconversation is created.

One innovative aspect of the subject matter described in thisspecification is embodied in methods that include the actions of:receiving, at a server, a topic for a real-time conversation from auser; receiving, at the server, location information related to alocation of the user; creating, at the server, a real-time conversationobject that includes the received topic; tagging the created real-timeconversation object with the received location information; indexing,based on the received topic and the received location information, thetagged real-time conversation object with respect to other real-timeconversation objects; and providing the tagged real-time conversationobject in response to a search for real-time conversation objectsreceived from another user.

Another innovative aspect of the subject matter described in thisspecification is embodied in methods that include the actions of:receiving, at a server, location information related to a location of auser; determining a plurality of real-time conversation objects that areassociated with locations within an area related to the receivedlocation of the computing device, the location associated with each ofthe plurality of real-time conversation objects indicating a location ofa user at the time the user requested creation of the real-timeconversation object; and sending, to a computing device of the user,information representing the determined real-time conversation objects.

Another innovative aspect of the subject matter described in thisspecification is embodied in methods that include the actions of:receiving, at a server, location information related to a location of auser; determining a plurality of real-time conversation objects that areassociated with locations within an area related to the receivedlocation of the user and associated with a threshold level of messageactivity over a certain period of time; and sending, to a computingdevice of the user, information representing the selected real-timeconversation objects.

Other embodiments of these aspects include corresponding systems,apparatus, and computer programs, configured to perform the actions ofthe methods, encoded on computer storage devices. A system of one ormore computers can be so configured by virtue of software, firmware,hardware, or a combination of them installed on the system that inoperation cause the system to perform the actions. One or more computerprograms can be so configured by virtue having instructions that, whenexecuted by data processing apparatus, cause the apparatus to performthe actions.

These and other embodiments may each optionally include one or more ofthe following features. For instance, the location information mayreceived from a computing device of the user and based on an output of aGlobal Positioning System (GPS) sensor included in the computing deviceof the user. Alternatively or additionally, the actions may include:receiving, from the user, a list of other users to invite to beassociated with the created real-time conversation object; sending, tothe other users included in the received list, invitations to beassociated with the created real-time conversation object; receiving,from one or more of the other users, an acceptance of the invitation;and updating the created real-time conversation object to includeindicators of the one or more other users that accepted the invitation.

Indexing the tagged real-time conversation object may include updating,based on the location information, an index of real-time conversationobjects stored on the server to include the tagged real-timeconversation object. Updating the index of real-time conversationobjects stored on the server to include the tagged real-timeconversation object may include sorting the real-time conversationobjects included in the index based on locations associated with each ofthe real-time conversation objects. Updating the index of real-timeconversation objects stored on the server to include the taggedreal-time conversation object may include sorting the real-timeconversation objects included in the index based on a level of messageactivity over a certain period of time associated with each real-timeconversation object.

The actions may further include receiving a request from the user tocreate the real-time conversation object. Receiving location informationrelated to the location of the user may include receiving locationinformation that indicates the location of the user at the time the userrequested the creation of the real-time conversation object. And taggingthe created real-time conversation object with the received locationinformation may include tagging the created real-time conversationobject with the location of the user at the time the user requested thecreation of the real-time conversation object and maintaining thelocation with which the created real-time conversation object is taggedregardless of whether a current location of the user changes.

The actions may further include receiving, at the server, a selection ofa real-time conversation objects from the determined real-timeconversation objects; and sending, to the computing device of the user,a link to the selected real-time conversation object. The action mayfurther include receiving, from the computing device of the user,message information to be posted to the real-time conversation object;and updating the real-time conversation object with the received messageinformation and the time at which the message information was received.

Determining a plurality of real-time conversation objects may includedetermining a plurality of real-time conversation objects that areassociated with a threshold level of message activity over a certainperiod of time. Determining a plurality of real-time conversationobjects may also include determining a plurality of real-timeconversation objects that are associated with one or more other userswith whom the user of the computing device has indicated a relationship.

The subject matter described in this specification provides severaladvantages. For example, real-time conversations created by the systemsdescribed herein do not need to be associated with a particular businessor venue (e.g., a restaurant). Similarly, the real-time conversationsmay be associated with any topic. In other words, users that createreal-time conversations are not limited to a list of pre-selectedtopics. In addition, the systems described herein allow users to quicklydiscover the most relevant real-time conversations that are associatedwith locations near a user's current location.

The details of one or more embodiments of the subject matter describedin this specification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages of thesubject matter will become apparent from the description, the drawings,and the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an example system for creating a conversation.

FIG. 2 is a flow diagram of an example method for creating and indexinga conversation.

FIGS. 3A-3C illustrate examples of interfaces for use in the creation ofa conversation object.

FIG. 4 illustrates an example system for discovering and participatingin a conversation.

FIG. 5 is a flow diagram of an example method for discovering andparticipating in a conversation.

FIGS. 6A and 6B illustrate examples of interfaces for use in thediscovery of a conversation.

FIGS. 7A and 7B illustrate examples of interfaces for use in theparticipation in a conversation.

FIG. 8 is a block diagram illustrating an example of a computer system.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

Following is a description of systems and processes for creating andhosting interactive, real-time conversations based on a user's location.Real-time conversations provide a platform for users to exchangemessages in a continuously streaming environment. As will be describedin more detail with reference to the figures, the described systemharnesses the mobility of modern computing devices and allows a user tocreate a real-time conversation based on the user's location and anytopic the user chooses.

There are various types of real-time conversations. One example suchexample is instant messaging, a form of direct, text-based chattingcommunication where the messages are pushed to participants inreal-time. Other examples include Internet Relay Chat (IRC) and certainforms of mobile text messaging. However, the real-time conversationsreferred to herein are not limited to any of these implementations andencompass any types of conversation platforms that permit the exchangeof messages in real-time.

FIG. 1 illustrates an example system for creating a real-timeconversation. The conversation system 100 can be implemented as, forexample, computer programs running on one or more computers in one ormore locations that are coupled to each other through a network. Theconversation system 100 includes a conversation database 102, aconversation object creator 104, and a conversation indexer 106.

The conversation database 102 stores real-time conversation objects thatrepresent real-time conversations between users. Each real-timeconversation object is related to a location and a topic, as well asother parameters (e.g., time). The conversation object creator 104receives various parameters regarding a proposed real-time conversation,including the location and the topic, and creates a real-timeconversation object that includes the received parameters. Beyond alocation and topic, the parameters of a real-time conversation mayinclude, for example, a list of users that should be invited to join theconversation, an icon representing the conversation, and one or moremessages to begin the conversation.

Each real-time conversation object stores the entire contents of thereal-time conversation. For example, the real-time conversation objectstores all previous messages contributed to the conversation, the timeand date each message was contributed, the user that contributed themessage, identifiers of all users that have joined the conversation, andan indication of those members that are currently participating in theconversation. Moreover, each real-time conversation object provides aplatform for a plurality of users associated with a common location tointeractively communicate about a geographically relevant topic.However, in the creation of a real-time conversation object, the user isnot limited to a predetermined list of topics or categories. Rather, auser may organically create a real-time conversation based on any topicrelevant to the user's location.

The conversation indexer 106 stores the real-time conversation objectscreated by the conversation object creator 104 in the conversationdatabase 102 and indexes the created real-time conversation object withrespect to a plurality of other real-time conversation objects stored inthe conversation database. By indexing the created conversation, theconversation indexer 106 enables other users to search for the createdconversation in the conversation database 102.

A user 112 generally interacts with the conversation system 100 througha user device 114. For example, the user device 114 can be a mobiledevice coupled to the conversation system 100 through a local areanetwork (LAN) or wide area network (WAN), e.g., the Internet. The user112 may interface with the conversation system 100 in various ways. Forexample, the user 112 may interface with the conversation system 100 byaccessing a webpage associated with the conversation system 100 on abrowser application on the user device 114. Alternatively oradditionally, an application may be installed on the user device 114that, when executed, provides an interface to the conversation system100.

When creating a real-time conversation, the user 112 may be presentedwith a creation screen 116. Through interaction with the creation screen116, the user 112 may submit conversation parameters (e.g., location andtopic) to the conversation system 100. For example, while walking downElm Street, the user 112 may encounter a house that is on fire. Throughcreation screen 116, the user 112 may submit, to the conversation system100, conversation parameters 118 that include a location of “Elm Street”and a topic of “Fire.”

The conversation object creator 104 receives and creates a real-timeconversation object based on the conversation parameters 118. Theconversation indexer 106 stores the real-time conversation objectscreated by the conversation object creator 104 in the conversationdatabase 102 and indexes the created conversation object with respect toa plurality of other real-time conversation objects stored in theconversation database. The conversation indexer 106 provides users withthe ability to discover what is happening around them right now. Theconversation system 100 returns data 120 regarding the created andindexed conversation object to the user device 114. The data 120 mayinclude, for example, a link to the real-time conversation object sothat the user device 114 may display the conversation and allow the user112 to interact with the conversation. Moreover, when the user device114 accesses a screen providing a list of conversations 122, the createdand indexed conversation may be included.

In certain implementations, protective steps may be taken with respectto user privacy. For example, depending on the particular type of databeing used, the services being provided, and the ability to providecertain services with modified data, a system may provide users with theopportunity to opt in/out of services that may collect personalinformation, may partially or fully anonymize data so as to preventpersonally identifiable information from being disclosed, and mayperform similar operations with respect to user location data, userpreference data, and other data relating to users of the system.

FIG. 2 is a flow diagram of an example method 200 for creating andindexing a real-time conversation. For convenience, the method 200 isdescribed with reference to a system of one or more servers thatperforms the method. The system can be, for example, the conversationsystem 100 described above with reference to FIG. 1.

The system receives a topic for a real-time conversation from a user(202). The topic may be identified by any string of characters that theuser chooses to use to represent the conversation. For example, thetopic could be “Concert in the Park” or “Free doughnuts on the corner!”The user may provide her own topic or may select from a list of topicsprovided by the system. The topic of conversation provides an indicationto other users of the subject of the conversation.

The system also receives location information for the conversation(204). The location information may indicate the present location of theuser. The location information may also indicate a location other than abusiness, for example, a street, a neighborhood, or a landmark. Thelocation information may be determined in various manners. In someimplementations, the location information may correspond to a locationprovided by the user device from which the user is submitting thelocation information. In other implementations, the user may specify thelocation information by manually providing an indication of the locationinformation by, for example, selecting the location from a map displayedby the user device or by providing an address of the location.

The system may also receive other parameters related to the real-timeconversation. For example, the user may specify an icon to represent thereal-time conversation. The user may select the icon from a list oficons provided by the system or the user may provide her own icon from adifferent source. Additionally or alternatively, the user may specify alist of other users she would like to invite to the real-timeconversation. When the system receives a list of other users to inviteto the real-time conversation, the system may send a link to thereal-time conversation object to the other users. The other users mayaccess the link to the real-time conversation object and participate inthe real-time conversation.

Additionally or alternatively, the user may specify whether thereal-time conversation is to be made public or private. The system maymake public conversations accessible to any other users that search forthem. On the other hand, the system my limit accessibility of privateconversations to those other users that the user creating the real-timeconversation invites to join. Additionally or alternatively, the usermay provide one or more messages to be included in the real-timeconversation object. In other words, the user may provide a seed for theconversation by including an initial message to which other users mayrespond.

The system creates a real-time conversation object that includes thereceived topic and location information (206). The system may alsoinclude, in the real-time conversation object, any of the other receivedparameters related to the conversation. The real-time conversationobject may be any data structure that relates the received parametersand the messages related to the conversation. For example, the systemmay create a real-time conversation object by creating an XML structurethat represents the conversation. Alternatively, the system may create areal-time conversation object by creating a database object related tothe conversation.

The created real-time conversation object includes a thread of messagesreceived by the system from one or more users. Once created, the systemcontinuously updates the thread of messages to include any additionalmessages that are received in relation to the real-time conversation. Insome implementations, the system may also include information related tothe state of the conversation in the real-time conversation object. Forexample, the real-time conversation object may include informationindicating the number of other users that have joined the conversationor that have actively participated in the conversation, as well as anindication of these other users' identities. In other words, thereal-time conversation object represents on ongoing exchange in whichusers contribute in real-time.

The system may use the indication of the identities other users who havejoined the real-time conversation to send updates of the conversation tothe other users. The real-time conversation object may includeinformation indicating the last time that a message was posted in theconversation, which the system may use to sort the real-timeconversation object with respect to other real-time conversationobjects.

Moreover, the system may tag the real-time conversation object with thereceived location information. In particular, the real-time conversationobject may be updated to store a representation of the locationinformation. The system may use any format for specifying the locationof the real-time conversation.

In some implementations, the location information associated with thereal-time conversation object may be static. For example, the real-timeconversation object may be permanently tagged with the locationspecified by the user during the creation of the real-time conversationobject. In other implementations, the location information associatedwith the real-time conversation object may be dynamic. For example, asthe user that created the real-time conversation object moves, thelocation information associated with the real-time conversation objectmay be continuously or periodically updated with the new location of theuser.

The system indexes the created real-time conversation object withrespect to a plurality of real-time conversation objects such that thecreated conversation object is searchable by other users (208). Thesystem stores a plurality of real-time conversation objects. Eachreal-time conversation object may include any combination of theconversation parameters described above, as well as any otherparameters.

In some implementations, each real-time conversation object includes atleast a location and a topic. The system may index the real-timeconversation objects based on one or more of the parameters included inthe real-time conversation object. For example, the system may index thereal-time conversation objects based on the location and the topic ofthe conversation. Indexing the real-time conversation objects allows thesystem to make the real-time conversation objects searchable by users,as will be described in greater detail below with regard to FIG. 5.

FIGS. 3A-3C illustrate examples of interfaces for use in the creation ofa real-time conversation object. The interfaces are described withreference to a system of one or more servers that provide the interfacesto a user and a user device. The system can be, for example, theconversation system 100 described above with reference to FIG. 1. Theuser device may be, for example, a mobile telephone.

The interface 300 shown in FIG. 3A represents a portal for a user toprovide parameters in the process of creating a real-time conversation.The interface 300 includes various regions. The interface 300 mayinclude a region 302 that provides a user with a choice of icons withwhich to represent the real-time conversation being created. Theinterface 300 may include a region 304 that permits a user to specifythe name or topic of the real-time conversation. The region 304 mayinclude text field in which a user may enter a name or topic.Alternatively or additionally, the region 304 may include a pull-downmenu that includes a list of suggested topics or names. However, theinterface 300 is designed so as to permit a user to freely create areal-time conversation without limits on the subject or category of theconversation.

The interface 300 may include a region 306 that permits a user tospecify a list of other users that the user would like to invite to jointhe real-time conversation being created. The region 306 may include asearch field that permits a user to search for other users to include inthe invitation list and/or may include a pull-down menu that includes alist of other users that are associated with the user creating thereal-time conversation (e.g., a list of “friends”).

The interface 300 may include a region 308 that relates to a locationassociated with the real-time conversation. In some implementations,where the location of the conversation is automatically determined andprovided by the user device, the region 308 may include a map showingthe location of the user device and an advisory to the user that theconversation will be visible to nearby users, if the conversation is notmade private.

In some implementations, where the location of the conversation ismanually provided by the user device, the region 308 may include a mapwith which the user may interact to specify a location for theconversation. Alternatively or additionally, the region 308 may includea text field in which a user may enter, for example, an address orkeyword to specify a location for the conversation.

The interface 300 may include a region 308 that permits a user to entera message to be included in the conversation. The region 308 may includea text field in which a user may enter a message. The interface 300 mayinclude other regions for specifying other parameters related to theconversation being created. For example, the interface may include aregion that permits the user to designate the conversation as eitherprivate or public.

Generally, the interface 300 provides a single mechanism through which auser may create a conversation about any topic. The user need not entera location and have a topic selected for her. Similarly, the user neednot search through a list of pre-selected locations, for example, a listof businesses. Rather, the interface 300 allows a user to specify anytopic that is relevant to the user's experience at a given location.

The interface 320 shown in FIG. 3B represents a status of a createdconversation. The interface 320 includes various regions. The interface320 may include a region 322 that indicates the number of users thathave joined the real-time conversation. The interface 320 may include aregion 324 that permits a user to join the conversation. Region 324 maybe a button that, when pressed, causes the system to join the user tothe conversation.

Region 326 may include a list of users that are currently joined to thereal-time conversation. For users included in the region 326, theinterface 320 may include an indication of the user's identity, the lasttime the user participated in the real-time conversation, and an iconthat represents the user. For example, the indication of the user'sidentity may be the user's name or a handle associated with the user.The indication of the last time the user participated in the real-timeconversation may include the date and time at which the user lastcontributed a message to the real-time conversation. When a user iscurrently viewing the message thread of the real-time conversation oractively typing a message to be posted in the message thread, theindication of the last time the user participated in the conversationmay indicate that the user is “in conversation,” “currentlyparticipating,” or some variation thereof. Thus, participating in andbeing joined to a real-time conversation are distinct states. When auser is participating in a real-time conversation, the user is activelyinteracting with the real-time conversation object. On the other hand, auser joins a conversation regarding which the user wants to be notifiedof updates and with which the user generally wants to be associated.

Once a user has joined a real-time conversation, the user may access theconversation's settings through, for example, an interface similar tothe interface 330 that is shown in FIG. 3C. The interface 330 includesvarious regions. The interface 330 may include a region 332 that permitsa user to change the tone or music emitted by the user device when thereal-time conversation is updated with, for example, a new message. Theinterface 330 may include a region 334 that indicates the name or topicof the real-time conversation. In some implementations, the region 334may permit a user that has joined the real-time conversation to changethe name or topic. Alternatively, the region 334 may only permit theuser who created the real-time conversation to change the name or topicand may simply display the name or topic to all other users.

The interface 330 may include a region 336 that indicates whether thereal-time conversation is public or private. Similar to region 334,region 336 may permit a user that has joined the real-time conversationto change the setting of the conversation from public to private andvice versa. Alternatively, the region 334 may only permit the user whocreated the real-time conversation to change the setting of theconversation from public to private and vice versa.

The interface 330 may include a region 338 that permits a user to managethe notifications that the user device provides to the user in relationto the real-time conversation. For example, the user device may beconfigured to notify the user when a new message has been posted in thereal-time conversation or only when messages from certain users havebeen posted in the real-time conversation. Additionally oralternatively, the user device may be configured to notify the user whenanother user has joined and/or left the real-time conversation.Additionally or alternatively, the user device may be configured tonotify the user when the user is located within a certain distance ofthe location associated with the real-time conversation. The interface330 may include a region 340 that permits a user to leave the real-timeconversation.

FIG. 4 illustrates an example system for finding and joining real-timeconversations. Once a real-time conversation object has been created,the conversation system 400 provides users with the ability to find outwhat is happening around them in real-time. As a user moves betweenstreets or neighborhoods, the conversation system 400 will present theuser with a list of real-time conversations that are both relevant tothe user's location and are being actively conducted concurrent with theuser's travels.

The conversation system 400 can be implemented as, for example, computerprograms running on one or more computers in one or more locations thatare coupled to each other through a network. The conversation system 400may be implemented on the same one or more computers as conversationsystem 100 as described above with regard to FIG. 1. However,conversation system 400 may be implemented as a separate system on oneor more other computers.

The conversation system 400 includes a conversation database 402, aconversation search engine 404, and a conversation participationinterface 406. The conversation database 402 stores indexed conversationobjects that represent real-time conversations between users. Eachreal-time conversation object may be related to a location and a topic,as well as other parameters. As described above, the stored real-timeconversation objects are indexed by the parameters to which thereal-time conversation objects are associated.

The conversation search engine 404 may receive an indication of one ormore parameters based upon which conversation search engine 404 searchesfor real-time conversations. For example, the conversation search engine404 may receive an indication of a location based upon whichconversation search engine 404 searches for real-time conversations.Alternatively or additionally, the conversation search engine 404 mayreceive one or more search terms related to the name or topic of areal-time conversation. The conversation search engine 404 may searchthe stored indexes for the received parameters and return a list ofreal-time conversations related to the received parameters.

The conversation participation interface 406 provides an interfacethrough which a user may view and post messages to a selected real-timeconversation. The conversation participation interface 406 may receive amessage from a user device and store the message in a message threadincluded in the corresponding real-time conversation object. Theconversation participation interface 406 may also receive requests froma user to join and/or leave a real-time conversation and update a listof associated users included in the corresponding real-time conversationobject. The conversation participation interface 406 may also receiveupdates to the settings associated with a real-time conversation object,as described above with regard to FIG. 3C.

A user 412 generally interacts with the search system 400 through a userdevice 414. For example, the user device 414 can be a mobile devicecoupled to the conversation system 400 through a local area network(LAN) or wide area network (WAN), e.g., the Internet. The user 412 mayinterface with the conversation system 400 in various ways. For example,the user 412 may interface with the conversation system 400 by accessinga webpage associated with the conversation system 400 on a browserapplication on the user device 414. Alternatively or additionally, anapplication may be installed on the user device 414 that, when executed,provides an interface to the conversation system 400.

When creating a real-time conversation, the user 412 may be presentedwith a conversation search screen 416. Through interaction with theconversation search screen 416, the user 412 may submit conversationparameters (e.g., location or topic) to the conversation system 400 andsearch for existing real-time conversations. For example, while walkingdown Elm Street, the user 412 may encounter a house that is on fire.Through conversation search screen 416, the user 412 may submit, to theconversation system 400, search parameters 418 that include a locationof “Elm Street” and/or a topic of “Fire.” These parameters 418 may bespecified by the user and/or provided automatically by the user device414. For example, as a user walks onto Elm Street, the user device 414may provide the user's location to the conversation system 400 in orderto obtain a list of conversations relevant to Elm Street.

The conversation search engine 404 receives the search parameters 418and searches indexes related to the stored real-time conversationobjects using the received search parameters 418. The conversationsearch engine 404 may return data 420 that includes a set of links toreal-time conversation objects resulting from the search. The userdevice 414 may display the set of links to real-time conversationobjects as a list of conversations. The user may then select a real-timeconversation from the list of conversations to view.

When a user selects a real-time conversation from the list, the userdevice 414 may access the link to the corresponding real-timeconversation object. When accessing a real-time conversation, the user412 may be presented with a conversation participation screen 422. Theconversation participation screen 422 provides a portal to theconversation participation interface 406. Through interaction with theconversation search screen 416, the user 412 may view the variouscontents of the selected real-time conversation object. For example, theuser 412 may be presented with the messages in the message threadincluded in the real-time conversation object.

Moreover, the user 412 may interact with the conversation participationscreen 422 to send changes 424 to conversation participation interface406 regarding the real-time conversation object. For example, the user412 may post a new message to the message thread. The conversationparticipation interface 406 receives the changes 424 and may update thereal-time conversation object stored in conversation database 402accordingly. The conversation participation interface 406 may also sendupdates 426 to user device 414 related to any real-time conversationobjects to which user 412 is joined.

FIG. 5 is a flow diagram of an example method 500 discovering andparticipating in a real-time conversation. For convenience, the method500 is described with reference to a system of one or more servers thatperforms the method. The system can be, for example, the conversationsystem 400 described above with reference to FIG. 4.

The system receives location information from a user (502). The locationinformation may indicate the present location of the user. The locationinformation may also indicate a location other than a business, forexample, a street, a neighborhood, or a landmark. The locationinformation may be determined in various manners. In someimplementations, the location information may correspond to a locationof the user device from which the user is submitting the locationinformation. For example, the user device may determine its locationthrough a global positioning sensor (GPS) included in the user device,through a process of cell tower triangulation, through a process ofevaluating a Wi-Fi network connection's signal strength, though an IPaddress assigned to the user device, or through any combination of theseor other methods. In other implementations, the user may specify thelocation information by manually providing an indication of the locationinformation by, for example, selecting the location from a map displayedby the user device or by providing an address of the location.

The system may receive other search parameters. For example, the systemmay receive one or more search terms related to the name or topic of areal-time conversation. Alternatively or additionally, the system mayreceive identifiers associated with users that created or are joined toone or more real-time conversations.

The system determines one or more real-time conversation objects thatrelate to the received location information (504). The one or moreconversation objects may include other conversation parameters (e.g., atopic). To determine the one or more real-time conversation objects thatrelate to the received location information, the system may search oneor more indexes stored by the system. The indexes may include variousconversation parameters associated with the real-time conversationobjects, including, for example, a location associated with each of thereal-time conversation objects. In some implementations, the systemdetermines one or more real-time conversation objects that relate to thereceived location information by comparing the received locationinformation with the location associated with each of the real-timeconversation objects. The system may, for example, determine that areal-time conversation object relates to the received locationinformation where the received location information is within a certaindistance of the location associated with the real-time conversationobject.

The system may also search for real-time conversation objects based onuser preferences. For example, the user may specify that she only wantsto search for and be presented with real-time conversations that herfriends created or have joined. In other words, the system allows a userto specifically determine what her nearby friends are doing.Alternatively, the user may specify the distance within which thelocations associated with real-time conversation objects should belocated in order to be included in the returned results. The system mayutilize the stored user preferences in conjunction with the specifiedconversation parameters to search the one or more indexes stored by thesystem.

The system may present the user with an interface that includes the oneor more determined real-time conversation objects, for example, theinterface described below with regard to FIG. 6B. The system receives,from the user, a selection of a real-time conversation object from theone or more determined real-time conversation objects (506). Inimplementations where an interface includes the one or more determinedconversation objects, the user may select a real-time conversationobject from the one or more determined conversation objects included inthe interface. The user device from which the user selects the real-timeconversation object may include a list of links to the one or moredetermined conversation objects. When the user selects the real-timeconversation object, the user device may send a request for the link tothe system. Thus, the system may receive the request for the linkassociated with the selected conversation object.

The system accesses the selected conversation object (508). In someimplementations, for example, where the system receives a request for alink associated with a selected conversation object, the system accessesthe selected conversation object by accessing the link associated withthe real-time conversation object. The system may send the accessedconversation object to the user device from which the real-timeconversation object was selected. The user device may present theaccessed conversation object to the user via an interface, for example,the interface shown in FIGS. 7A and 7B.

The system may receive, from the user, a message associated with theaccessed conversation object (510). For example, through interactionwith an interface that presents the accessed conversation object to theuser on the user device, the user may enter and submit a message for thereal-time conversation. The system updates the real-time conversationobject to include the received message (512). Thus, the system mayreceive the message entered by the user and update the real-timeconversation object to include the received message.

FIGS. 6A and 6B illustrate examples of interfaces for use in finding areal-time conversation object. The interfaces are described withreference to a system of one or more servers that provide the interfacesto a user and a user device. The system can be, for example, theconversation system 400 described above with reference to FIG. 4. Theuser device may be, for example, a mobile telephone.

The interface 600 shown in FIG. 6A represents a menu screen for anapplication running on the user device. The application may, among otherfunctions, provide the interface through which the user interacts withthe system. The interface 600 may include various links to the functionsprovided by the application. For example, the interface 600 may includea link titled “Nearby” 602, which links to a function for searching thesystem for real-time conversations that are near in location to thelocation of the user device. The interface 600 may include a region 604that may provide an indication of new notifications received by the userdevice. The notifications may be similar to those described above withregard to region 338 of interface 330.

The interface 610 shown in FIG. 6B represents results from searching thesystem for real-time conversations that are near in location to thelocation of the user device. For example, when a user selects the link602 from the interface 600, the system may search one or more indexesstored by the system that include various conversation parametersassociated with real-time conversation objects, including, for example,a location associated with each of the real-time conversation objects.The system may determine one or more real-time conversation objects thatrelate to the location of the user device by determining that thelocation of the user device is within a certain distance of the locationassociated with the determined conversation objects.

The interface 610 may present the user with a list of the determinedreal-time conversation objects from the system's search. The interface610 may include multiple regions for organizing the determinedconversation in different manners. For example, the interface 610 mayinclude a region 612 that lists nearby real-time conversations that arepopular over a long period of time. The system may determine thelong-term popularity of a real-time conversation in various ways,including, for example, by analyzing the total number of messages postedto the real-time conversation since its creation and/or the total numberof users joined to the real-time conversation. The interface 610 mayalso include a region 614 that lists nearby real-time conversations thatare currently popular. The system may determine the current popularityof a real-time conversation in various ways, including, for example,analyzing the number of users currently participating in the real-timeconversation or the number of messages posted to the real-timeconversation within the last day.

A real-time conversation included in the list of conversations displayedby the interface 610 may be represented in the list by a number ofconversation parameters. For example, a real-time conversation may berepresented by its topic, its icon, the number of users joined to thereal-time conversation, the names of friends of the user of the userdevice joined to the real-time conversation, and/or the number ofmessages posted to the real-time conversation that have not been read bythe user. The interface may also include a button 616 that allows theuser to create a new conversation, if, for example, the system does notreturn a real-time conversation related to the topic about which theuser wants to talk.

FIGS. 7A and 7B illustrate examples of interfaces for use inparticipating in a real-time conversation. The interfaces are describedwith reference to a system of one or more servers that provide theinterfaces to a user and a user device. The system can be, for example,the conversation system 400 described above with reference to FIG. 4.The user device may be, for example, a mobile telephone.

Each of the interfaces 700 and 701 illustrated in FIGS. 7A and 7B,respectively, represent a visual representation of an accessed real-timeconversation object. Interface 700 represents an example where thereal-time conversation has not yet been joined by the user. Conversely,the interface 701 represents an example where the real-time conversationhas been joined by the user. However, the interfaces 700 and 701 includemany of the same elements, which will be described together.

Interfaces 700 and 701 may both include a region 702 that indicates thetopic or name of the real-time conversation object. Interfaces 700 and701 may both include a region 704 that represents the number of membersjoined to the real-time conversation and a list of identifiersassociated with the joined users. For example, the region 704 mayinclude a list of icons associated with a user (e.g., a picture of theuser). The region 704 may allow the user to scroll through the list.

Interfaces 700 and 701 may both include a region 706 that lists themessages posted to the real-time conversation. In addition to the textof the message itself, each message included in the region 706 may berepresented by one or more identifiers associated with the user thatposted the message and an indication of when the message was posted. Theone or more identifiers associated with the user that posted the messagemay include, for example, the name of the user and a photo of the user.The region 706 may allow the user to scroll through all of the messagesposted to the real-time conversation. Additionally, the region 706 mayorder the listed messages in various manners. For example, the messagesmay be listed by the time at which the message was posted and/or by therelationship between the posting user and the viewing user.

Interfaces 700 and 701 may both include a region 708 that indicateswhether other users that have joined the real-time conversation arecurrently typing messages to post to the conversation. Interfaces 700and 701 may both include a region 710 that permits a user to enter amessage to be instantly posted to the real-time conversation. The region710 may include a text field that allows the user to enter a message anda submit button that allows the user to post the entered message.

However, with regard to interface 700, a user who is viewing or browsingthe real-time conversation, but has not joined the real-timeconversation, may be prevented from posting a message to theconversation. The interface 700 may prevent a user from interacting withregion 710 altogether. Alternatively, if a user interacts with region710, interface 700 may trigger a pop-up notification that asks the userwhether the user would like to join the real-time conversation.

The interface 700 may include a region 712 that, when interacted with,permits a user to join the real-time conversation. Conversely, interface701 may include region 714 that, when interacted with, permits a user toview and edit the settings of the real-time conversation. For example,region 714 may be a button that, when pressed by the user, presents theuser with an interface 330. Interface may also include a region 716that, when interacted with, permits a user to invite other users to jointhe real-time conversation. For example, when a user selects region 716,the system may send a notification (e.g., an e-mail) to the invitedusers with a link to the real-time conversation object and an identityof the inviting user. The system may not permit a user who has notjoined the real-time conversation to view or edit the settings of thereal-time conversation of invite other users to join the real-timeconversation.

FIG. 8 is a block diagram of computing devices 800, 850 that may be usedto implement the systems and methods described in this document, aseither a client or as a server or plurality of servers. Computing device800 is intended to represent various forms of digital computers, forexample, laptops, desktops, workstations, personal digital assistants,servers, blade servers, mainframes, and other appropriate computers.Computing device 850 is intended to represent various forms of mobiledevices, for example, personal digital assistants, cellular telephones,smartphones, and other similar computing devices. The components shownhere, their connections and relationships, and their functions, aremeant to be exemplary only, and are not meant to limit implementationsof the inventions described and/or claimed in this document.

Computing device 800 includes a processor 802, memory 804, a storagedevice 806, a high-speed interface 808 connecting to memory 804 andhigh-speed expansion ports 810, and a low speed interface 812 connectingto low speed bus 814 and storage device 806. Each of the components 802,804, 806, 808, 810, and 812, are interconnected using various busses,and may be mounted on a common motherboard or in other manners asappropriate. The processor 802 can process instructions for executionwithin the computing device 800, including instructions stored in thememory 804 or on the storage device 806 to display graphical informationfor a GUI on an external input/output device, for example, display 816coupled to high speed interface 808. In other implementations, multipleprocessors and/or multiple buses may be used, as appropriate, along withmultiple memories and types of memory. Also, multiple computing devices800 may be connected, with each device providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system).

The memory 804 stores information within the computing device 800. Insome implementations, the memory 804 is a computer-readable medium. Inother implementations, the memory 804 is a volatile memory unit orunits. In still other implementations, the memory 804 is a non-volatilememory unit or units.

The storage device 806 is capable of providing mass storage for thecomputing device 800. In some implementations, the storage device 806 isa computer-readable medium. In various different implementations, thestorage device 806 may be a floppy disk device, a hard disk device, anoptical disk device, or a tape device, a flash memory or other similarsolid state memory device, or an array of devices, including devices ina storage area network or other configurations. In some implementations,a computer program product is tangibly embodied in an informationcarrier. The computer program product contains instructions that, whenexecuted, perform one or more methods (e.g., those described above). Theinformation carrier is a computer- or machine-readable medium, forexample, the memory 804, the storage device 806, or memory on processor802.

The high speed controller 808 manages bandwidth-intensive operations forthe computing device 800, while the low speed controller 812 manageslower bandwidth-intensive operations. Such allocation of duties isexemplary only. In some implementations, the high-speed controller 808is coupled to memory 804, display 816 (e.g., through a graphicsprocessor or accelerator), and to high-speed expansion ports 810, whichmay accept various expansion cards (not shown). In theseimplementations, low-speed controller 812 is coupled to storage device806 and low-speed expansion port 814. The low-speed expansion port,which may include various communication ports (e.g., USB, Bluetooth,Ethernet, wireless Ethernet) may be coupled to one or more input/outputdevices, for example, a keyboard, a pointing device, a scanner, or anetworking device (e.g., a switch or router), through a network adapter.

The computing device 800 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 820, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 824. Inaddition, it may be implemented in a personal computer (e.g., a laptopcomputer 822). Alternatively, components from computing device 800 maybe combined with other components in a mobile device (not shown), forexample, device 850. Each of such devices may contain one or more ofcomputing device 800, 850, and an entire system may be made up ofmultiple computing devices 800, 850 communicating with each other.

Computing device 850 includes a processor 852, memory 864, aninput/output device, for example, a display 854, a communicationinterface 866, and a transceiver 868, among other components. The device850 may also be provided with a storage device, for example, amicrodrive or other device, to provide additional storage. Each of thecomponents 850, 852, 864, 854, 866, and 868, are interconnected usingvarious buses, and several of the components may be mounted on a commonmotherboard or in other manners as appropriate.

The processor 852 can process instructions for execution within thecomputing device 850, including instructions stored in the memory 864.The processor may also include separate analog and digital processors.The processor may provide, for example, for coordination of the othercomponents of the device 850, for example, control of user interfaces,applications run by device 850, and wireless communication by device850.

Processor 852 may communicate with a user through control interface 858and display interface 856 coupled to a display 854. The display 854 maybe, for example, a TFT LCD display or an OLED display, or otherappropriate display technology. The display interface 856 may compriseappropriate circuitry for driving the display 854 to present graphicaland other information to a user. The control interface 858 may receivecommands from a user and convert them for submission to the processor852. In addition, an external interface 862 may be provide incommunication with processor 852, so as to enable near areacommunication of device 850 with other devices. External interface 862may provide, for example, for wired communication (e.g., via a dockingprocedure) or for wireless communication (e.g., via Bluetooth or othersuch technologies).

The memory 864 stores information within the computing device 850. Insome implementations, the memory 864 is a computer-readable medium. Inother implementations, the memory 864 is a volatile memory unit orunits. In still other implementations, the memory 864 is a non-volatilememory unit or units. Expansion memory 874 may also be provided andconnected to device 850 through expansion interface 872, which mayinclude, for example, a SIMM card interface. Such expansion memory 874may provide extra storage space for device 850, or may also storeapplications or other information for device 850. Specifically,expansion memory 874 may include instructions to carry out or supplementthe processes described above, and may include secure information also.Thus, for example, expansion memory 874 may be provide as a securitymodule for device 850, and may be programmed with instructions thatpermit secure use of device 850. In addition, secure applications may beprovided via the SIMM cards, along with additional information, forexample, placing identifying information on the SIMM card in anon-hackable manner.

The memory may include for example, flash memory and/or MRAM memory, asdiscussed below. In some implementations, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, for example, the memory 864,expansion memory 874, or memory on processor 852.

Device 850 may communicate wirelessly through communication interface866, which may include digital signal processing circuitry wherenecessary. Communication interface 866 may provide for communicationsunder various modes or protocols, for example, GSM voice calls, SMS,EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, amongothers. Such communication may occur, for example, throughradio-frequency transceiver 868. In addition, short-range communicationmay occur using a Bluetooth, WiFi, or other such transceiver (notshown). In addition, GPS receiver module 870 may provide additionalwireless data to device 850, which may be used as appropriate byapplications running on device 850.

Device 850 may also communication audibly using audio codec 860, whichmay receive spoken information from a user and convert it to usabledigital information. Audio codex 860 may likewise generate audible soundfor a user through, for example, a speaker in a handset of device 850.Such sound may include sound from voice telephone calls, may includerecorded sound (e.g., voice messages, music files, etc.) and may alsoinclude sound generated by applications operating on device 850.

The computing device 850 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 880. It may also be implemented as part of asmartphone 882, personal digital assistant, or other similar mobiledevice.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention. Forexample, various forms of the flows shown above may be used, with stepsre-ordered, added, or removed. Also, although several applications ofthe payment systems and methods have been described, it should berecognized that numerous other applications are contemplated.Accordingly, other embodiments are within the scope of the followingclaims.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinvention or of what may be claimed, but rather as descriptions offeatures that may be specific to particular embodiments of particularinventions. Certain features that are described in this specification inthe context of separate embodiments can also be implemented incombination in a single embodiment. Conversely, various features thatare described in the context of a single embodiment can also beimplemented in multiple embodiments separately or in any suitablesubcombination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Particular embodiments of the subject matter have been described. Otherembodiments are within the scope of the following claims. For example,the actions recited in the claims can be performed in a different orderand still achieve desirable results. As one example, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In certain implementations, multitasking and parallelprocessing may be advantageous.

What is claimed is:
 1. A method comprising: receiving, at a server, atopic for a real-time conversation from a user; receiving, at theserver, location information related to a location of the user;creating, at the server, a real-time conversation object that includesthe received topic; tagging the created real-time conversation objectwith the received location information; indexing, based on the receivedtopic and the received location information, the tagged real-timeconversation object with respect to other real-time conversationobjects; and providing the tagged real-time conversation object inresponse to a search for real-time conversation objects received fromanother user.
 2. The method of claim 1, wherein the location informationis received from a computing device of the user and based on an outputof a Global Positioning System (GPS) sensor included in the computingdevice of the user.
 3. The method of claim 1, further comprising:receiving, from the user, a list of other users to invite to beassociated with the created real-time conversation object; sending, tothe other users included in the received list, invitations to beassociated with the created real-time conversation object; receiving,from one or more of the other users, an acceptance of the invitation;and updating the created real-time conversation object to includeindicators of the one or more other users that accepted the invitation.4. The method of claim 1, wherein indexing the tagged real-timeconversation object includes updating, based on the locationinformation, an index of real-time conversation objects stored on theserver to include the tagged real-time conversation object.
 5. Themethod of claim 4, wherein updating the index of real-time conversationobjects stored on the server to include the tagged real-timeconversation object includes sorting the real-time conversation objectsincluded in the index based on locations associated with each of thereal-time conversation objects.
 6. The method of claim 4, whereinupdating the index of real-time conversation objects stored on theserver to include the tagged real-time conversation object includessorting the real-time conversation objects included in the index basedon a level of message activity over a certain period of time associatedwith each real-time conversation object.
 7. The method of claim 1,further comprising receiving a request from the user to create thereal-time conversation object, wherein: receiving location informationrelated to the location of the user includes receiving locationinformation that indicates the location of the user at the time the userrequested the creation of the real-time conversation object; and taggingthe created real-time conversation object with the received locationinformation includes tagging the created real-time conversation objectwith the location of the user at the time the user requested thecreation of the real-time conversation object and maintaining thelocation with which the created real-time conversation object is taggedregardless of whether a current location of the user changes.
 8. Asystem comprising: one or more computers and one or more storage devicesstoring instructions that are operable, when executed by the one or morecomputers, to cause the one or more computers to perform operationscomprising: receiving a topic for a real-time conversation from theuser; receiving location information related to a location of the user;creating a real-time conversation object that includes the receivedtopic; tagging the created real-time conversation object with thereceived location information; indexing, based on the received topic andthe received location information, the tagged real-time conversationobject with respect to other real-time conversation objects; andproviding the tagged real-time conversation object in response to asearch for real-time conversation objects received from another user. 9.The system of claim 8, wherein the location information is received froma computing device of the user and based on an output of a GlobalPositioning System (GPS) sensor included in the computing device of theuser.
 10. The system of claim 8, wherein the stored instructions includeinstructions that are operable, when executed by the one or morecomputers, to cause the one or more computers to perform operationscomprising: receiving, from the user, a list of other users to invite tobe associated with the created real-time conversation object; sending,to the other users included in the received list, invitations to beassociated with the created real-time conversation object; receiving,from one or more of the other users, an acceptance of the invitation;and updating the created real-time conversation object to includeindicators of the one or more other users that accepted the invitation.11. The system of claim 8, wherein the stored instructions are operable,when executed by the one or more computers, to cause the one or morecomputers to perform operations comprising: indexing the taggedreal-time conversation object by updating, based on the locationinformation, an index of real-time conversation objects stored on theserver to include the tagged real-time conversation object.
 12. Thesystem of claim 11, wherein the stored instructions are operable, whenexecuted by the one or more computers, to cause the one or morecomputers to perform operations comprising: updating the index ofreal-time conversation objects stored on the server to include thetagged real-time conversation object by sorting the real-timeconversation objects included in the index based on locations associatedwith each of the real-time conversation objects.
 13. The system of claim11, wherein the stored instructions are operable, when executed by theone or more computers, to cause the one or more computers to performoperations comprising: updating the index of real-time conversationobjects stored on the server to include the tagged real-timeconversation object by sorting the real-time conversation objectsincluded in the index based on a level of message activity over acertain period of time associated with each real-time conversationobject.
 14. The system of claim 8, wherein the stored instructionsinclude instructions that are operable, when executed by the one or morecomputers, to cause the one or more computers to perform operationscomprising: receiving a request from the user to create the real-timeconversation object, wherein the stored instructions are operable, whenexecuted by the one or more computers, to cause the one or morecomputers to: receive location information related to the location ofthe user by receiving location information that indicates the locationof the user at the time the user requested the creation of the real-timeconversation object; and tag the created real-time conversation objectwith the received location information by tagging the created real-timeconversation object with the location of the user at the time the userrequested the creation of the real-time conversation object andmaintaining the location with which the created real-time conversationobject is tagged regardless of whether a current location of the userchanges.
 15. A nonvolatile computer storage medium encoded with acomputer program, the program comprising instructions that, whenexecuted by one or more computers, cause the one or more computers toperform operations comprising: receiving a topic for a real-timeconversation from the user; receiving location information related to alocation of the user; creating a real-time conversation object thatincludes the received topic; tagging the created real-time conversationobject with the received location information; indexing, based on thereceived topic and the received location information, the taggedreal-time conversation object with respect to other real-timeconversation objects; and providing the tagged real-time conversationobject in response to a search for real-time conversation objectsreceived from another user.
 16. The medium of claim 15, wherein thelocation information is received from a computing device of the user andbased on an output of a Global Positioning System (GPS) sensor includedin the computing device of the user.
 17. The medium of claim 15, whereinthe program includes instructions that, when executed by the one or morecomputers, cause the one or more computers to perform operationscomprising: receiving, from the user, a list of other users to invite tobe associated with the created real-time conversation object; sending,to the other users included in the received list, invitations to beassociated with the created real-time conversation object; receiving,from one or more of the other users, an acceptance of the invitation;and updating the created real-time conversation object to includeindicators of the one or more other users that accepted the invitation.18. The medium of claim 15, wherein the instructions, when executed byone or more computers, cause the one or more computers to performoperations comprising: indexing the tagged real-time conversation objectby updating, based on the location information, an index of real-timeconversation objects stored on the server to include the taggedreal-time conversation object.
 19. The medium of claim 18, wherein theinstructions, when executed by one or more computers, cause the one ormore computers to perform operations comprising: updating the index ofreal-time conversation objects stored on the server to include thetagged real-time conversation object by sorting the real-timeconversation objects included in the index based on locations associatedwith each of the real-time conversation objects.
 20. The medium of claim18, wherein the instructions, when executed by one or more computers,cause the one or more computers to perform operations comprising:updating the index of real-time conversation objects stored on theserver to include the tagged real-time conversation object by sortingthe real-time conversation objects included in the index based on alevel of message activity over a certain period of time associated witheach real-time conversation object.
 21. The medium of claim 15, whereinthe program includes instructions that, when executed by the one or morecomputers, cause the one or more computers to perform operationscomprising: receiving a request from the user to create the real-timeconversation object, wherein the instructions, when executed by one ormore computers, cause the one or more computers to: receive locationinformation related to the location of the user by receiving locationinformation that indicates the location of the user at the time the userrequested the creation of the real-time conversation object; and tag thecreated real-time conversation object with the received locationinformation by tagging the created real-time conversation object withthe location of the user at the time the user requested the creation ofthe real-time conversation object and maintaining the location withwhich the created real-time conversation object is tagged regardless ofwhether a current location of the user changes.